<!DOCTYPE HTML>
<html lang="en">
<head>
<meta name="copyright" content="Copyright (c) 2024 IBM Corporation and others. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
<meta charset="utf-8">
<link rel="STYLESHEET" href="../../book.css" type="text/css">
<title>Incompatibilities between Eclipse 4.32 and 4.33</title>
</head>
<body>
<h1>Incompatibilities Between Eclipse 4.32 and 4.33</h1>

<p>
  Eclipse changed in incompatible ways between 4.32 and 4.33 in ways that affect
  plug-ins. The following entries describe the areas that changed and provide
  instructions for migrating 4.32 plug-ins to 4.33. Note that you only need to look
  here if you are experiencing problems running your 4.32 plug-in on 4.33.
</p>
<p>
See also the list of <a href="../removals.html">deprecated API removals</a> for this release.
</p>

<ol>
<li><a href="#upstream-bundles">Several bundles renamed for 3rd party libraries</a></li>
</ol>

<hr>

<!-- ############################################## -->

<h2 id="native-fragments-merge">1. Multiple Platform-specific Fragments Merged Into Their Host</h2>
<p>
	The following platform-specific fragments have been merged into their respective host bundle:
</p>
<ul>
	<li><code>org.eclipse.core.resources.win32.win32.x86_64</code></li>
	<li><code>org.eclipse.core.filesystem.win32.x86_64</code></li>
	<li><code>org.eclipse.core.net.linux</code></li>
	<li><code>org.eclipse.core.net.win32</code></li>
</ul>
<p>
	All functionality formerly provided through these platform-specific fragments is now provided by the fragment's host bundle alone and no code change is required.
	If any of the mentioned fragments is referenced in a PDE <em>feature.xml</em> or listed as content of a product definition it just has to be removed.
</p>

</body>
</html>